System and Method for Gaining Access of Devices Based on User&#39;s Identity

ABSTRACT

A system and a method for gaining access of devices based on a user&#39;s identity are disclosed. The method comprises a target device detecting a user worn accessory present in vicinity of a target device. Upon detection, the target device receives a user identity (UID) from the user worn accessory. The user worn accessory sends the UID based on verification of user&#39;s body data. Upon receiving the UID, the target device matches the UID with a list of known UID&#39;s to identify access rights assigned to the target device. Based on the identified access rights, the target device provides access to the user. Thus, the user may automatically get an access without handling the target device.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a divisional application of U.S. application Ser.No. 16/030,910, filed on Jul. 10, 2018, which is a continuation of U.S.Provisional Application No. 62/530,314, filed on Jul. 10, 2017.

FIELD OF THE DISCLOSURE

The present disclosure is generally related to automatic identificationof a user, and more particularly related to automatic identification ofthe user by user worn accessories.

BACKGROUND

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also correspond toimplementations of the claimed technology.

User devices such as smart phones often consist of sensitive user data.Thus, access of the user device needs to be restricted from other usersto maintain privacy and to avoid fraudulence. There exist a lot oftechniques for verifying identity of a user, for maintaining limitedaccess of the user devices. Such identity verification techniques useone of passwords, patterns, and biometrics such as face, fingerprints,finger veins, and retina.

The limitation associated with such verification methods comprises theeffort taken by a user to unlock the user device for each time. Usage ofbiometric sensors in the user device also increases overall cost of theuser device. Many times, the user also needs to make multiple attemptsto unlock the device due to calibration errors and poor recognition bythe sensors.

Another problem faced by the user is theft of their user devices. A userloses all his confidential data in case of loss of his personal device.Thus, there remains a need for automatic identification of the user bythe user device to allow access to the user. Further, a method to avoidtheft of the user devices is also desired

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate various embodiments of systems,methods, and embodiments of various other aspects of the disclosure. Anyperson with ordinary skills in the art will appreciate that theillustrated element boundaries (e.g. boxes, groups of boxes, or othershapes) in the figures represent one example of the boundaries. It maybe that in some examples one element may be designed as multipleelements or that multiple elements may be designed as one element. Insome examples, an element shown as an internal component of one elementmay be implemented as an external component in another, and vice versa.Furthermore, elements may not be drawn to scale. Non-limiting andnon-exhaustive descriptions are described with reference to thefollowing drawings. The components in the figures are not necessarily toscale, emphasis instead being placed upon illustrating principles.

FIG. 1 illustrates a network connection diagram of a system 100 forgaining access of devices based on a user's identity, according to anembodiment.

FIG. 2 illustrates different components of a user worn accessory i.e. aheadphone 102-1.

FIG. 3 illustrates a flowchart 300 of a method for gaining access ofdevices based on a user's identity, according to an embodiment.

FIG. 4 illustrates a flowchart 400 of a method for gaining access ofdevices based on a user's identity, according to an embodiment.

DETAILED DESCRIPTION

Some embodiments of this disclosure, illustrating all its features, willnow be discussed in detail. The words “comprising,” “having,”“containing,” and “including,” and other forms thereof, are intended tobe equivalent in meaning and be open ended in that an item or itemsfollowing any one of these words is not meant to be an exhaustivelisting of such item or items, or meant to be limited to only the listeditem or items.

It must also be noted that as used herein and in the appended claims,the singular forms “a,” “an,” and “the” include plural references unlessthe context clearly dictates otherwise. Although any systems and methodssimilar or equivalent to those described herein can be used in thepractice or testing of embodiments of the present disclosure, thepreferred, systems and methods are now described.

Embodiments of the present disclosure will be described more fullyhereinafter with reference to the accompanying drawings in which likenumerals represent like elements throughout the several figures, and inwhich example embodiments are shown. Embodiments of the claims may,however, be embodied in many different forms and should not be construedas limited to the embodiments set forth herein. The examples set forthherein are non-limiting examples and are merely examples among otherpossible examples.

FIG. 1 illustrates a network connection diagram of the system 100 forgaining access of devices based on a user's identity, according to anembodiment. FIG. 1 illustrates user worn accessones (102-1 to 102-3)communicating with a target device 104. The target device 104communicates with a remote server 108 through a communication network106. The target device 104 comprises a processor 110, interface(s) 112,memory 114, transceiver 116, and proximity sensor 118.

The communication network 106 may be implemented using at least onecommunication technique selected from Visible Light Communication (VLC),Worldwide Interoperability for Microwave Access (WiMAX), Long termevolution (LTE), Wireless local area network (WLAN), Infrared (IR)communication, Public Switched Telephone Network (PSTN), IntegratedServices Digital Network (ISDN), Broadband, cellular, Optical Fibrenetwork, Radio waves, and other known communication techniques andprotocols.

The processor 110 may execute an algorithm stored in the memory 114 forgaining access of devices based on a user's identity. The processor 110may also be configured to decode and execute any instructions receivedfrom one or more other electronic devices or server(s). The processor110 may include one or more general purpose processors (e.g., INTELmicroprocessors) and/or one or more special purpose processors (e.g.,digital signal processors or Xilinx System On Chip (SOC) FieldProgrammable Gate Array (FPGA) processor). The processor 110 may beconfigured to execute one or more computer-readable programinstructions, such as program instructions to carry out any of thefunctions described in this description.

The interface(s) 112 may be used by a user to program the target device104. The interface(s) 112 may be used either to accept an input from theuser or to provide an output to the user, or performing both theactions. The interface(s) 112 may either be a Command Line Interface(CLI) or a Graphical User Interface (GUI).

The memory 114 may include, but is not limited to, fixed (hard) drives,magnetic tape, floppy diskettes, optical disks, Compact Disc Read-OnlyMemories (CD-ROMs), and magneto-optical disks, semiconductor memories,such as ROMs, Random Access Memories (RAMs), Programmable Read-OnlyMemories (PROMs), Erasable PROMs (EPROMs), Electrically Erasable PROMs(EEPROMs), flash memory, magnetic or optical cards, or other type ofmedia/machine-readable medium suitable for storing electronicinstructions.

In one embodiment, a user may wear at least one of the user wornaccessory (102-1 to 10-3). The user worn accessory may be any of aheadphone 102-1, a smart wristband 102-2, a smart watch 102-3, and anyother accessory that could be used for gaining access of devices basedon a user's identity. In one case, the user may wear the headphone102-1. Successively, the proximity sensor 118, present in the targetdevice 104, may detect the headphone 102-1 to be present in vicinity.The proximity sensor may utilize a communication technique selected froma group consisting of Wireless Fidelity (Wi-Fi), Bluetooth, Near FieldCommunication (NFC), Infrared (IR), and Radio Frequency Identification(RFID).

Post detecting the headphone 102-1, the target device 104 may verify ifthe user is wearing the headphone 102-1 or the headphone 102-1 is keptidle. The target device 104 may receive such verification from theheadphone device 102-1. In one case, the headphone device 102-1 maycomprise a pressure sensor for determining a current usage by the useri.e. the user wearing the headphone device 102-1. The pressure sensormay be present in at least one ear cup of right and left speaker of theheadphone device 102-1, or in the headband attaching the ear cups. Theheadphone device 102-1 upon determining about being worn by the user maytransmit the UID to the target device 104.

The target device 104 may receive the user identity (UID) from theheadphone 102-1. In one case, the UID may be received in an encryptedformat. The encryption may be performed by an encryption module 210present in the headphone 102-1. Further, the encryption module 210 mayutilize an encryption technique such as Rivest Shamir Adleman (RSA),Triple Data Encryption Standard (DES), Blowfish, Twofish, AdvancedEncryption Standard (AES) and the like. The encryption may be performedusing a 32-bit or 64-bit encryption standard. The encryption techniquemay be selected based on a user input or selection.

The target device 104 may receive the User Identity (UID) by thetransceiver 116. The received UID may be present in an encrypted formatin one case. A de-encryption module 120 present in the target device 104may de-encrypt the received UID. The de-encrypted UID may be any of analphanumeric key, image, and answers to security questions, or any otheridentifier unique to the user. In one case, the alphanumeric key may bereceived as the UID.

In one embodiment, the headphone 102-1 may determine if the user isactually wearing the headphone 102-1 or the headphone 102-1 is keptidle. The headphone 102-1 may send the UID only upon confirming that theuser is wearing the headphone 102-1. For such detection, motion sensors206 present in the headphone 102-1 may be used to capture motion data.The motion data may be analyzed by a processor 202 of the headphone102-1, to confirm if the headphone 102-1 is being worn by the user. Postconfirming, a transceiver 204 of the headphone 102-1 may send the UID tothe target device 104. FIG. 2 illustrates different components of theheadphone 102-1.

In another embodiment, the UID may be sent upon verifying if theheadphone 102-1 is being worn by an owner of the headphone 102-1. Forsuch verification, the user's identity may be determined based on user'sbody data. The user's body data may be captured using body sensors 208present in the headphone 102-1. The body sensors 208 may be configuredto monitor body parameters selected from a group consisting of heartrate, heart rate variability, respiratory rate, skin temperature, bodyposture, coughing, smoking, drinking, speaking, and breathing. Therecorded body parameters may be analyzed by the processor 202 to verifyif the owner of the headphone 102-1 is actually wearing the headphone102-1. Upon successful verification, a transceiver 204 of the headphone102-1 may transmit the UID to the target device 104.

In one embodiment, successive to receiving the UID, the target device104 may match the UID with a list of known UID's stored in the memory114. The target device 104 may match the received UID for identifyingaccess rights assigned to the UID. Based on the access rights assignedto the UID, the target device 104 may provide an access to the user.

In one embodiment, the target device 104 may be either of a smart phone,laptop, tablet, and a phablet. The target device 104 is shown to be asmart phone as an example. The smart phone may allow its access to theuser based on a successful verification of identity of the user wearingthe user worn accessory. The identity of the user may be verified withthe user worn accessory, in an above described manner. Thus, an owner ofthe smart phone may automatically get an access of the smart phone withhelp of the user worn accessory.

In another embodiment, the target device 104 may be a physical accesssystem. The physical access system may allow movement of the user basedon a successful verification of identity of the user, wearing the userworn accessory. The identity of the user may be verified with the userworn accessory, in an above described manner. Thus, a user mayautomatically find access through the physical access system with helpof the user worn accessory.

In one embodiment, the target device 104 and the user worn accessory maycomprise a button (either soft button or hard button) for terminating aconnection between them. The button may be integrated with a biometricsensor, such as a fingerprint scanner. The fingerprint scanner may allowswitching ON and OFF the button only upon verifying an identity of theuser. Further, the target device 104 and the user worn accessory maycomprise an alarm. The alarm may be implemented using speakers and/orLight Emitting Devices (LEDs). The alarm may be raised in response to atrigger generated by the target device 104. The target device 104 maygenerate the trigger in case of unauthorized termination of connectionbetween the target device 104 and the user worn accessory. For example,if a thief snatches the target device 104 or the user worn accessory andruns away, the alarm may be raised and may not be deactivated till anauthorized user switches OFF the alarm.

It is well understood that the above explained embodiments of presentdisclosure may be implemented with modifications lying within scope ofthe present disclosure. It is also understood that the above disclosuremay allow a user for gaining access of different devices. A few of theapplications may comprise automatic access of devices such as a laptop,smart phone, and tablet. Further, the user may also get recognized byphysical access systems, attendance systems, banking systems, and othersystem where identity of an individual may need to be verified. Usingthe above described methodology, user preferences may also be setautomatically in an environment, based on the user's identity. A fewexamples of setting the user preferences may include setting up oftemperate, favorite music, lighting conditions, humidity conditions, andselecting a floor number on control panel of a lift.

FIG. 3 illustrates a flowchart 300 of a method of gaining access ofdevices based on a user's identity, according to an embodiment. FIG. 3comprises a flowchart 300 that is explained in conjunction with theelements disclosed in FIG. 1.

The flowchart 300 of FIG. 3 shows the architecture, functionality, andoperation for gaining access of devices based on a user's identity. Inthis regard, each block may represent a module, segment, or portion ofcode, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat in some alternative implementations, the functions noted in theblocks may occur out of the order noted in the drawings. For example,two blocks shown in succession in FIG. 3 may in fact be executedsubstantially concurrently or the blocks may sometimes be executed inthe reverse order, depending upon the functionality involved. Anyprocess descriptions or blocks in flowcharts should be understood asrepresenting modules, segments, or portions of code which include one ormore executable instructions for implementing specific logical functionsor steps in the process, and alternate implementations are includedwithin the scope of the example embodiments in which functions may beexecuted out of order from that shown or discussed, includingsubstantially concurrently or in reverse order, depending on thefunctionality involved. In addition, the process descriptions or blocksin flow charts should be understood as representing decisions made by ahardware structure such as a state machine. The flowchart 300 starts atthe step 302 and proceeds to step 308.

At step 302, a target device 104 may detect a user worn accessory 102-1(referred to using 102 for simplicity) present in vicinity. In oneembodiment, the user worn accessory 102 may be detected by a proximitysensor 118 of the target device 104.

At step 304, the target device may receive a user identity (UID)transmitted by the user worn accessory 102. The UID may be transmittedby the user worn accessory 102 based on verification of user's bodydata. In one embodiment, the user's body data may be captured by bodysensors 208, transmitted by a transceiver 204 of the user worn accessory102, and received by a transceiver 116 of the target device.

At step 306, the UID may be matched with a list of known UID's stored ina memory 114 of the target device 104. The UID may be matched toidentify access rights set for the UID. In one embodiment, the UID maybe matched by a processor 202 of the user worn accessory 102.

At step 308, an access of the target device 104 may be provided based onthe access rights set for the UID. In one embodiment, the access may beprovided a processor 110 of the target device 104.

FIG. 4 illustrates a flowchart 400 of another method of gaining accessof devices based on a user's identity, according to an embodiment. FIG.4 comprises a flowchart 400 that is explained in conjunction with theelements disclosed in FIG. 1.

The flowchart 400 of FIG. 4 shows the architecture, functionality, andoperation for gaining access of devices based on a user's identity. Inthis regard, each block may represent a module, segment, or portion ofcode, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat in some alternative implementations, the functions noted in theblocks may occur out of the order noted in the drawings. For example,two blocks shown in succession in FIG. 4 may in fact be executedsubstantially concurrently or the blocks may sometimes be executed inthe reverse order, depending upon the functionality involved. Anyprocess descriptions or blocks in flowcharts should be understood asrepresenting modules, segments, or portions of code which include one ormore executable instructions for implementing specific logical functionsor steps in the process, and alternate implementations are includedwithin the scope of the example embodiments in which functions may beexecuted out of order from that shown or discussed, includingsubstantially concurrently or in reverse order, depending on thefunctionality involved. In addition, the process descriptions or blocksin flow charts should be understood as representing decisions made by ahardware structure such as a state machine. The flowchart 400 starts atthe step 402 and proceeds to step 414.

At step 402, a target device 104 may detect a user worn accessory 102present in vicinity. In one embodiment, the user worn accessory 102 maybe detected by a proximity sensor 118 of the target device 104.

At step 404, a connection may be established between the target device104 and the user worn accessory 102. In one embodiment, the connectionmay be established by a processor 202 of the user worn accessory 102.

At step 406, the target device may receive a user identity (UID) fromthe user worn accessory 102. The UID may be transmitted by the user wornaccessory 102 based on verification of user's body data. In oneembodiment, the user's body data may be captured by body sensors 208,transmitted by a transceiver 204 of the user worn accessory 102, andreceived by a transceiver 116 of the target device 104.

At step 408, the UID may be matched with a list of known UID's stored ina memory 114 of the target device 104. The UID may be matched toidentify access rights set for the UID. In one embodiment, the UID maybe matched by the processor 202 of the user worn accessory 102.

At step 410, an access of the target device 104 may be provided based onthe access rights set for the UID. In one embodiment, the access may beprovided a processor 110 of the target device 104.

At step 412, an unauthorized termination of connection between thetarget device 104 and the user worn accessory 102 may be identified. Inone embodiment, the unauthorized termination may be identified by theprocessor 110 of the target device 104.

At step 414, a trigger may be sent to the user worn accessory 102 forgenerating an alarm. The trigger may be sent based on the identificationof unauthorized termination. In one embodiment, the trigger for alarmmay be sent by the processor 110 of the target device 104.

Embodiments of the present disclosure may be provided as a computerprogram product, which may include a computer-readable medium tangiblyembodying thereon instructions, which may be used to program a computer(or other electronic devices) to perform a process. Thecomputer-readable medium may include, but is not limited to, fixed(hard) drives, magnetic tape, floppy diskettes, optical disks, compactdisc read-only memories (CD-ROMs), and magneto-optical disks,semiconductor memories, such as ROMs, random access memories (RAMs),programmable read-only memories (PROMs), erasable PROMs (EPROMs),electrically erasable PROMs (EEPROMs), flash memory, magnetic or opticalcards, or other type of media/machine-readable medium suitable forstoring electronic instructions (e. g., computer programming code, suchas software or firmware). Moreover, embodiments of the presentdisclosure may also be downloaded as one or more computer programproducts, wherein the program may be transferred from a remote computerto a requesting computer by way of data signals embodied in a carrierwave or other propagation medium via a communication link (e.g., a modemor network connection).

What is claimed is:
 1. A computer implemented method of gaining accessof devices based on a user's identity, the computer implemented methodbeing executed on a target device and comprising: detecting, by aproximity sensor, a user worn accessory present in vicinity of thetarget device; receiving, by a transceiver, a user identity (UID) fromthe user worn accessory; matching, by a processor, the UID with a listof known UID's stored in a memory of the target device, to identifyaccess rights assigned to the UID; providing, by the processor, anaccess of the target device to the user, based on the access rightsassigned to the UID; and identifying, by the processor, an unauthorizedtermination of connection between the target device and the user wornaccessory; and sending, by the transceiver, a trigger to the user wornaccessory for generating an alarm based on the unauthorized terminationof connection.
 2. The method of claim 1, wherein the proximity sensorutilizes a communication request selected from a group consisting ofWireless Fidelity (Wi-Fi), Bluetooth, Near Field Communication (NFC),Infrared (IR), and Radio Frequency Identification (RFID).
 3. The methodof claim 1, wherein the user worn accessory is selected from a groupconsisting of headphone, smart wristband, and a smart watch.
 4. Themethod of claim 1, wherein the UID is at least one of an alphanumerickey, image, and answers to security questions.
 5. The method of claim 1,wherein the UID is sent by the user worn accessory based on verificationof user's body data recorded using body sensors.
 6. The method of claim5, wherein the body sensors are configured to monitor body parametersselected from a group consisting of heart rate, heart rate variability,respiratory rate, skin temperature, body posture, coughing, smoking,drinking, speaking, and breathing.
 7. The method of claim 1, wherein theUID is sent by the user worn accessory based on user's motion data. 8.The method of claim 1, further comprising encrypting the UID using anencryption technique selected from a group consisting of Rivest ShamirAdleman (RSA), Triple Data Encryption Standard (DES), Blowfish, Twofish,and Advanced Encryption Standard (AES).
 9. The method of claim 8,wherein the encryption technique is selected based on a user input. 10.(canceled)
 11. A system for gaining access of devices based on a user'sidentity, the system comprising: a processor; and a memory coupled tothe processor, wherein the processor is capable of executing programmedinstructions stored in the memory to: detect, by a proximity sensor, auser worn accessory present in vicinity of the target device; receive,by a transceiver, a user identity (UID) from the user worn accessory;match the UID with a list of known UID's stored in the memory, toidentify access rights assigned to the UID; provide an access of thetarget device to the user, based on access rights assigned to the UID;and generate an alarm, by at least one of the target device and the userworn accessory, upon unauthorized termination of connection between thetarget device and the user worn accessory.
 12. The system of claim 11,wherein the proximity sensor utilizes a communication request selectedfrom a group consisting of Wireless Fidelity (Wi-Fi), Bluetooth, NearField Communication (NFC), Infrared (IR), and Radio FrequencyIdentification (RFID).
 13. The system of claim 11, wherein the user wornaccessory is selected from a group consisting of headphone, smartwristband, and a smart watch.
 14. The system of claim 11, wherein theUID is at least one of an alphanumeric key, image, and answers tosecurity questions.
 15. The system of claim 11, wherein the UID is sentby the user worn accessory based on verification of user's body data,wherein the user's body data is captured using body sensors present onthe user worn accessory.
 16. The system of claim 15, wherein the bodysensors are configured to monitor body parameters selected from a groupconsisting of heart rate, heart rate variability, respiratory rate, skintemperature, body posture, coughing, smoking, drinking, speaking, andbreathing.
 17. The system of claim 11, wherein the UID is sent by theuser worn accessory based on user's motion data captured using motionsensors present on the user worn accessory.
 18. The system of claim 11,further comprising a pressure sensor present in the user worn accessoryfor determining a current usage of the user worn accessory andthereafter transmitting the UID to the target device based on thecurrent usage.
 19. (canceled)